home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
drivers
/
landr3.exe
/
LANDR3.TXT
< prev
next >
Wrap
Text File
|
1993-10-27
|
26KB
|
610 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Server LAN Drivers
DOCUMENT ID: TID013624
DOCUMENT REVISION: A
DATE: 06OCT93
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: LANDR3.EXE
NOVELL PRODUCT and VERSION:
NetWare 3.11
NetWare 3.12
NetWare 4.01
NetWare SFT III 3.11
ABSTRACT:
This file contains the latest certified Novell server drivers for NExxx.*
boards, plus TOKEN, TRXNET, and PCN2L. SFT III ability has been added.
──────────────────────────────────────────────────────────────────────────────
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
──────────────────────────────────────────────────────────────────────────────
SYMPTOM
Promiscuous mode was not supported by the ETHERTSM.NLM.
SYMPTOM
When running Ethernet_802.2 to the AS/400 HOST, intermittent disconnect
problems were experienced with NetWare for SAA 1.3x. This might be seen
more commonly with large file transfers.
SYMPTOM
General and custom LAN statistics for Ethernet, Token-ring, ARCnetT, and
Baseband PCN2L were unavailable.
SYMPTOM
MONITOR.NLM statistics Que depth showed that ECBs were incrementing when
they really weren't. This problem was only a cosmetic issue with the
display.
SYMPTOM
Loading the LAN driver a second time for a second frame type in the
AUTOEXEC.NCF would not load automatically when the board was set to
INT=2.
SOLUTION
Apply LANDR3.EXE.
Solution Specifics:
1. ETHERTSM.NLM in LANDR3.EXE now supports Promiscuous mode. The TSMs,
ETHERTSM.NLM, TOKENTSM.NLM, and FDDITSM.NLM now support NetWare
Management System 2.0.
2. ETHERTSM.NLM addresses the disconnect problem NetWare for SAA 1.3x.
3. The STATS.DOC in LANDR3.EXE documents general and custom LAN
statistics for Ethernet, TOKEN-ring, ARCNET, and Baseband PCN2L.
4. Server ODI drivers are now composed of three different NLMs. For
example when loading the NE2000.LAN, both ETHERTSM.NLM and
MSM31X.NLM will automatically load. When loading TOKEN.LAN, both
TOKENTSM.NLM and MSM31X.NLM will automatically load. The MSM31X.NLM
will always load and the TSM is specific to topology.
5. The TSMs now increment the Que depth properly on the display.
6. With the latest MSM31X.NLM, it is no longer necessary to apply XLOAD
when using interrupts 2 and 9 on a NetWare 3.11 server although it
is still okay to apply XLOAD.
7. MSM.NLM would not properly handle the problem of a server out of
memory condition when loading only. This is really a non-issue;
because if you did not have even enough memory to load your LAN
driver, you would have other problems as well.
8. MSM and MSM31X.NLM has been changed so that LSLENH.NLM and
LSLENH3.NLM should not have problems with third-party drivers that
do not use the ECB driver workspace properly.
9. With MSM31X.NLM in LANDR3.EXE, using the parameter I2 is no longer
required (on the load driver line in the AUTOEXEC.NCF) when the
board is set to Interrupt 2 and loading a second frame type.
Example:
LANDR2.EXE - Load lines:
LOAD NE3200 INT=2 PORT=xxx NAME=aaa FRAME=Ethernet_802.3 I2
BIND IPX TO aaa
LOAD NE3200 INT=2 PORT=xxx NAME=bbb FRAME=Ethernet_802.2 I2
BIND IPX TO bbb
LANDR3.EXE - Load lines:
LOAD NE3200 INT=2 PORT=xxx NAME=aaa FRAME=Ethernet_802.3
BIND IPX TO aaa
LOAD NE3200 INT=2 PORT=xxx NAME=bbb FRAME=Ethernet_802.2
BIND IPX TO bbb
10. LANDR3.EXE contains the following Novell server drivers. The
following files are the latest certified operating system drivers
available:
MSM NLM - 4.01 Media Support Module (MSM)
MSM31X NLM - 3.11 and 3.12 Media Support Module (MSM)
ETHERTSM NLM - Ethernet Topology Support Module (TSM)
TOKENTSM NLM - Token Topology Support Module
RXNETTSM NLM - Arcnet Topology Support Module
PCN2LTSM NLM - PCN2L Topology Support Module
FDDITSM NLM - FDDI Topology Support Module
NE1000 LAN
NE2000 LAN
NE2 LAN
NE2_32 LAN
NE3200 LAN
NE1500T LAN
NE32HUB LAN
TOKENDMA LAN
TOKEN LAN
NTR2000 LAN - Novell NTR2000 TOKEN RING Driver
TRXNET LAN
PCN2L LAN
LSLENH NLM - LSL ENHANCED NLM.
PATCHMAN NLM
MONITOR NLM - REQUIRED with new drivers on NetWare 3.11
!NVL1201 CFG - NE32HUB CFG file
@7151 ADF - NE2_32 ADF file
!NVL0701 CFG - NE3200 CFG file
!NVL1301 CFG - NE32HUB TPE CFG file
!NVL1401 CFG - NE32HUB PME CFG file
!NVL1501 CFG - NE2000 plus CFG file
!NVL0901 CFG - NE2100/NE1500T CFG file
@7154 ADF - NE2 ADF file
FIRMLOAD COM - Use with TOKENDMA to load firmware
XLOAD EXE
XLOAD DOC
LDR001 PTF
LDR001 DOC
STATS DOC - Information for LAN statistics
LANDR3 TXT
PM311IO NLM - Use with SFT III 3.11 (Patchman)
LSLENH3 NLM - Use with SFT III 3.11
IOSHIM NLM - Needed when running NetWare SFT III 3.11 with
LSLENH3.NLM and the NE2000.LAN driver
---------------------------------------------------
Self-Extracting File Name: LANDR3.EXE Revision: A
Files Included Size Date Time
\
LANDR3.TXT (This File)
STATS.DOC 63446 10-06-93 3:55p
ETHERTSM.NLM 8841 09-28-93 2:41p
TOKENTSM.NLM 9040 09-30-93 3:30p
FDDITSM.NLM 7847 07-07-93 5:07p
MSM.NLM 15628 10-04-93 1.03p
MSM31X.NLM 16483 10-04-93 1:04p
NE2000.LAN 7356 10-08-93 10:47a
NE2100.LAN 7224 09-24-93 4:25p
NE1500T.LAN 7226 09-24-93 4:25p
TOKEN.LAN 10125 06-07-93 1:29p
TOKENDMA.LAN 10861 05-26-93 3:16p
RXNETTSM.NLM 6202 01-06-93 10:04a
PCN2LTSM.NLM 5691 01-30-93 11:32a
NE1000.LAN 4468 01-20-93 3:18p
PM311IO.NLM 8384 04-13-93 11:28a
LSLENH3.NLM 10500 06-02-93 11:34a
IOSHIM.NLM 1649 06-09-93 9:50a
NTR2000.LAN 10272 09-13-93 2:23p
TRXNET.LAN 3075 01-07-93 1:23p
PCN2L.LAN 4726 01-29-93 8:45p
LSLENH.NLM 11641 11-16-92 8:29a
PATCHMAN.NLM 9632 02-04-93 10:38a
MONITOR.NLM 117775 10-26-92 9:21a
!NVL1201.CFG 7378 03-26-92 9:08a
NE2.LAN 4954 10-08-93 10:44a
NE2_32.LAN 5066 05-12-93 4:03p
NE3200.LAN 13811 10-08-93 10:51a
NE32HUB.LAN 12266 01-27-93 9:11a
@7151.ADF 2346 07-26-89 5:08p
!NVL0701.CFG 2745 09-02-92 1:25p
!NVL1301.CFG 1169 03-12-92 2:28p
!NVL1401.CFG 986 06-10-92 4:02p
!NVL1501.CFG 11994 01-11-93 3:24p
!NVL0901.CFG 8293 10-04-90 10:42a
FIRMLOAD.COM 1628 01-04-91 8:57a
@7154.ADF 2657 04-27-92 1:54p
XLOAD.EXE 13872 08-06-91 4:47p
XLOAD.DOC 3472 07-06-92 11:00a
LDR001.PTF 52920 11-06-91 4:55p
LDR001.DOC 3200 07-06-92 11:00a
Installation Instructions:
Installing on NetWare 3.11 (Without SFT III)
*** WARNING ***
If you use the shipping NetWare 3.11 MONITOR.NLM, your server could
abend when viewing LAN statistics in MONITOR.NLM with these newer
drivers. The MONITOR.NLM included in this update corrects this
problem.
1. Rename the old .LAN, MONITOR.NLM, PATCHMAN.NLM files.
2. Copy all .LAN and .NLM files (except for PM311IO.NLM, LSLENH3.NLM,
and IOSHIM.NLM) into your SYSTEM directory. Do not use PM311IO.NLM,
LSLENH3.NLM, and IOSHIM.NLM on NetWare 3.11. These files are for
NetWare SFT III 3.11 ONLY.
3. Load LSLENH.NLM first. This will automatically load the
PATCHMAN.NLM.
4. Load the corresponding driver for your LAN card (<filename>.LAN).
This will automatically load MSM/MSM31X and xxxTSM.NLM.
Note: Loading the MSM.NLM will generate warnings that cause
MSM31X.NLM to be automatically loaded. This is normal. The warning
messages generated will be as follows:
MESSAGE
Loader cannot find public symbol:
The message will be followed by the public symbol name.
To eliminate the warning message on NetWare 3.1x, you can remove
MSM.NLM and rename MSM31X.NLM to MSM.NLM.
5. Verify that you are using the included MONITOR.NLM with these new
drivers.
Note: If you are also running NetWare for Macintosh, you may see a
conflict with the drivers. If you do, load file ATK306.EXE. This
file is available from your Novell Authorized Service Center (NASC),
Novell reseller, or from one of Novell's electronic distribution
tools (for example, NetWire on CompuServe or the Network Support
Encyclopedia on CD-ROM).
Installing on NetWare 3.12 or 4.01
1. Rename the old .LAN file.
2. Copy all new .LAN and new .NLM files except for PM311IO.NLM,
LSLENH3.NLM, IOSHIM.NLM, LSLENH.NLM and PATCHMAN.NLM into your
SYSTEM directory. The PM311IO.NLM, LSLENH3.NLM, and IOSHIM.NLM
files are for NetWare SFT III 3.11 ONLY. PATCHMAN.NLM applies to
NetWare 3.11 only. The LSLENH.NLM is built into the NetWare 3.12
and 4.01 operating system.
3. Load the corresponding driver for your LAN board (<filename>.LAN).
This will automatically load MSM/MSM31X and xxxTSM.NLM.
Note: Loading the MSM.NLM will generate warnings that cause
MSM31X.NLM to be automatically loaded. This is normal. The warning
messages generated will be as follows:
MESSAGE
Loader cannot find public symbol:
The message will be followed by the public symbol name.
To eliminate the warning message on NetWare 3.1x, you can remove
MSM.NLM and rename MSM31X.NLM to MSM.NLM.
Installing on NetWare SFT III 3.11
1. Rename the old xxx.LAN, xxxTSM.NLM, and MSMxxx.NLM files.
2. Copy the new xxx.LAN, xxxTSM.NLM, and MSMxxx.NLM files into the
directory of each server where files loaded from IOSTART.NCF are
loaded. These files should also be put into the SYSTEM directory of
the SYS: volume for easy server maintenance.
Do not use LSLENH.NLM, PATCHMAN.NLM, MONITOR.NLM, XLOAD.EXE, or
LDR001.PTF with NetWare SFT III 3.11. These files are for NetWare
3.11 only.
Do not use the included MONITOR.NLM with NetWare SFT III 3.11. Use
the shipping MONITOR.NLM with NetWare SFT III 3.11. LAN statistics
are not part of MONITOR.NLM in SFT III 3.11.
3. Copy PM311IO.NLM and LSLENH3.NLM into the directory of each server
where files loaded from IOSTART.NCF are loaded.
4. Add "load lslenh3" to the IOSTART.NCF of each server before the load
statement for the LAN drivers. This will automatically load
PM311IO.NLM.
5. Load the corresponding driver for your adapter (<filename>.LAN) in
the IOSTART.NCF of each server after the load statement for
LSLENH3.NLM. This will automatically load MSM/MSM31X and
xxxTSM.NLM.
Note: Loading MSM.NLM will generate warnings that cause MSM31X.NLM
to be automatically loaded. This is normal. The warning messages
generated will be as follows:
MESSAGE
Loader cannot find public symbol:
The message will be followed by the public symbol name.
To eliminate the warning message on NetWare SFT III 3.11, you can
remove MSM.NLM and rename MSM31X.NLM to MSM.NLM.
6. If you are using NE2000.LAN, copy IOSHIM.NLM and make sure it is
loaded before the LSLENH3.NLM.
Installing and Setting the IBM Token-Ring 16/4 Busmaster Server Adapter/A
The IBM Token-Ring 16/4 Busmaster Server Adapter/A is functionally
different from the IBM Token-Ring 16/4 Adapter/A in two ways:
■ Busmaster capability
Busmastering allows the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A to transfer between the network and the server's memory
without the aid of the server's CPU. The server's CPU can then
process other network tasks more quickly than it otherwise could.
■ Downloadable microcode
Downloading microcode allows you to upgrade the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A's firmware without replacing
any chips on the adapter. FIRMLOAD.COM (supplied by Novell) allows
you to download the firmware (supplied by IBM) to the adapter.
Before you install this adapter in a 3.1x server, you should have
designed your network and assembled the necessary hardware. If you have
any questions about Token-Ring hardware or network layout, see the Novell
IBM Token-Ring Network Supplement manual for further information.
For information concerning installation and configuration of the 16/4
Busmaster card, please refer to the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A Installation and Testing Instructions that accompany the
adapter. Additional information concerning the following setable
parameters can be found in the "change configuration" selection in the
Reference program:
■ Data rate
The default data rate for the adapter is 4 Mbps.
The other valid data rate is 16 Mbps.
Important: You must set all IBM Token-Ring 16/4 adapters on a ring
to use the same data rate (either 16 Mbps or 4 Mbps). Failure to do
so will cause network errors.
■ Interrupt level
The default is Interrupt 2.
Other valid levels include interrupts 3, 4, 5, 7, 10, 11, and 12.
■ I/O address
The default I/O address is 86A0-86AF.
Each valid address consists of a 16-byte block of RAM within the
Micro Channel machine. There are seven additional valid I/O
addresses: 96A0, A6A0, B6A0, C6A0, D6A0, E6A0, and F6A0.
Ensure each adapter installed in the machine has a unique I/O
address.
■ Arbitration level
The default arbitration level is E.
Other valid arbitration levels are 0, 1, 2, 3, 5, 6, 7, 8, 9, A, B,
C, and D.
Each busmaster adapter requires a unique arbitration level for
negotiating with other busmaster adapters within the same machine
for control of the microchannel bus.
■ Fairness
The default is to operate with fairness ON.
The other valid option is to operate with fairness OFF.
Fairness determines how a Micro Channel busmaster adapter negotiates
with other busmaster adapters within the same machine for control of
the microchannel bus.
For more information about arbitration and fairness, read the IBM
publication, PS/2 Hardware Technical Reference.
■ Bus release
The default is "Maximum."
The other valid setting is "Immediately."
The bus release setting determines how long a Micro Channel
busmaster adapter has to relinquish the bus when another adapter
preempts it during a DMA operation.
A setting of "Immediately" causes the adapter to relinquish control
of the Micro Channel bus upon receiving the preempt signal.
A setting of "Maximum" allows the adapter time to finish critical
DMA operations, resulting in better overall performance.
■ Early Token Release (ETR)
When the data rate is 16 Mbps, the default is to operate with ETR.
The other valid option is NO ETR.
Operation with ETR is not valid for Token-Rings with a data rate of
4 Mbps.
ETR can increase network performance by causing the adapter to
release the token immediately upon deencapsulating the data packet,
rather than after it has successfully transferred the deencapsulated
data to the next higher network protocol.
DOWNLOADING the Microcode
IMPORTANT
The Microcode must be downloaded to the Busmaster Server Adapter/A
each time the machine is powered up. This can be accomplished
manually (from the command line) or can be automated in a batch
file.
The IBM Token-Ring 16/4 Busmaster Server Adapter/A requires
microcode that is not resident on the adapter. The microcode is
contained in two files included on the adapter's option diskette
(supplied by IBM):
■ MONT400.BIN
■ WRTRAM.BIN
To download MONT400.BIN and WRTRAM.BIN to the adapter, you must use
FIRMLOAD.COM, a utility supplied by Novell.
When you have located these three files (including FIRMLOAD.COM),
complete the following steps:
1. Copy the MONT400.BIN, WRTRAM.BIN, and FIRMLOAD.COM files to the
same diskette (or to the same directory).
2. Change to drive or directory that contains MONT400.BIN,
WRTRAM.BIN, and FIRMLOAD.COM.
3. Type the following:
FIRMLOAD <Enter>
A message similar to the following appears:
MESSAGE
Novell Token-Ring DownLoad Utility for IBM DMA Bus Master
v1.00 (901129)(C) Copyright 1990 Novell Inc. All Rights
Reserved.
IBM Token-Ring DMA Bus Master FOUND in Slot 2;
Data Rate = 04 Mbps
DMA Level = 0E; Interrupt Level=02
Node Address = 1000 5A4F 00AE; Port = 86A0
IBM Token-Ring DMA Bus Master DownLoad SUCCESSFUL
IMPORTANT
Applies to NetWare 3.11 only
The loader portion of SERVER.EXE will need to be modified to
properly load the new TOKENDMA.LAN driver. To make this change in
SERVER.EXE, you need to use XLOAD.EXE and LDR001.PTF. Novell
recommends patching SERVER.EXE on NetWare 3.11 servers except
NetWare SFT III 3.11. NetWare 3.12 does not require the new loader
because it is built into SERVER.EXE.
For more information about XLOAD and LDR001, read XLOAD.DOC and
LDR001.DOC. XLOAD should always be applied when using interrupts 2
and 9 on Micro Channel bus machines.
* * * * * * * * * * * * * * * * * * * * * * * * * * * *
Patch History:
The server drivers originally provided in NE386.ZIP fixed the following:
■ These versions were rewritten to use the Media Support Module (MSM).
The MSM was the new tool (module) available to LAN driver developers
from Novell to develop better LAN drivers.
■ In some environments these new drivers could help solve
communication problems.
■ The file server could lock under a heavy load if it was a 486
machine and was using an NE2000 or an NE/2 network board. A race
condition existed where the last remote DMA write cycle of the
National Semiconductor DP8390 (on the network board) prematurely
terminated by writing to the Command Register with bit "RD2" set
before the remote DMA write cycle had completed. These later
versions of the drivers addressed the issue.
■ On certain networks with high traffic the adapter would stop
receiving.
LANDR2.EXE drivers additionally included the following enhancements:
■ The default frame type for ethernet drivers became Ethernet_802.2
rather than ethernet_802.3. The ETHERTSM.NLM detected if the driver
was being loaded on NetWare 3.11 and defaulted to Ethernet_802.3.
If the operating system wasn't NetWare 3.11, the default frame type
became Ethernet_802.2.
■ Drivers were updated to the latest Novell 4.0 specification.
■ NE2000.LAN was enhanced to use shared RAM for the NE2000+.
■ NE2100.LAN has been enhanced to take advantage of the new PCNET ISA
chip set from AMD. This allowed the new clones that have this
chipset to run faster.
■ NE3200.LAN had some performance enhancements. This newer driver in
combination with the newer .CFG file was more stable. When using
NE3200.LAN, Novell support recommended selecting EDGE TRIGGERED
interrupts when running the EISA configuration and using the latest
!NVL0701.CFG (DMA timing modified) file supplied in LANDRx.EXE.
■ TOKEN.LAN was enhanced to use the FAST or QUICK path available on
the IBM NASSAU II FRU #74F9415. This increased performance over
early TOKEN.LAN drivers using these boards in the file server. If
the driver didn't load with the IBM Token Ring adapter installed, it
was because the card was one of the newer adapters from IBM that
require the IBM-supplied driver (for example, TOKENBM.LAN).
■ TOKENDMA.LAN - This driver was more reliable than previous drivers.
Because the adapter was busmastering and not 32-bit, the driver had
to double buffer when writing above 16 MB of RAM. The issue did not
apply to servers with 16 MB or less of RAM.
TOKEN.LAN History
TOKEN.LAN v3.15 was used with Novell's Communications Server
NLM on a NetWare 3.11 server. It corrected lost connection
problems when a workstation was attached to a host through the
COM-Server. It also corrected a problem that v3.13 (the
version of the driver that currently ships with NetWare 3.11)
had with ABEND: GENERAL PROTECTION PROCESSOR EXCEPTION (GPPE).
This GPPE was caused by beaconing out on the ring.
■ TOKEN.LAN fixed a problem not parsing the NODE override correctly.
■ TOKEN.LAN v3.18 (920129)
TOKEN.LAN v3.18 provided the following corrective services:
■ Priority bits usage was modified from priority-1 to
priority-0.
■ Transmit LSL-ECBs are returned back to the operating
system if the ring is beaconing. This allowed the
TOKEN.LAN send queue to remain manageable until beaconing
conditions on the ring were corrected. The following
error message was resolved with this new TOKEN.LAN file:
MESSAGE
Lan receive buffer limit reached. All buffers are in
use. Possible causes are disk-channel bottleneck or
buffers lost.
■ TOKEN.LAN v3.18 included an engineering change to work
better with IBM Token-Ring 1988 firmware. If running a
PROTOCOL in addition to IPX, TOKEN.LAN assumed the 1988
IBM FIRMWARE transmitted frames in a particular order.
TOKEN.LAN was changed so that it made no assumptions
about the transmit order.
■ TRXNET.LAN - This driver was tested only with the Novell RX-NET
RX-NET/2 boards. It may or may not have worked with other cards or
brands. From a support standpoint third-party vendors should have
provided their own drivers for their cards.
■ PCN2L.LAN - History from PCN23X.EXE NetWare 3.11. This file
contained a revision of the NetWare 3.1x PCN2L.LAN file. The
PCN2L.LAN file fixed a Remote Program Load problem. The problem
occurred when booting a workstation, which received no response from
the server, and the counter, located in the upper-right-hand corner
of the workstation's screen, continued to increment.